-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: Channel Points Automatic Reward Redemption #34
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you forgot to add the handler to TwitchLib.EventSub.Websockets.Handler.Channel.ChannelPoints.Redemptions
namespace TwitchLib.EventSub.Websockets.Core.EventArgs.Channel; | ||
public class ChannelPointsAutomaticRewardRedemptionArgs : TwitchLibEventSubEventArgs<EventSubNotification<ChannelPointsAutomaticRewardRedemption>> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing new line
namespace TwitchLib.EventSub.Websockets.Core.EventArgs.Channel; | |
public class ChannelPointsAutomaticRewardRedemptionArgs : TwitchLibEventSubEventArgs<EventSubNotification<ChannelPointsAutomaticRewardRedemption>> | |
namespace TwitchLib.EventSub.Websockets.Core.EventArgs.Channel; | |
public class ChannelPointsAutomaticRewardRedemptionArgs : TwitchLibEventSubEventArgs<EventSubNotification<ChannelPointsAutomaticRewardRedemption>> |
@AoshiW Thanks for letting me know about the handler. I wasnt aware that it need an handler, since I am not entire familiar with the codebase yet. I tried to make the handler based of ChannelPointsCustomRewardRedemptionAddHandler.cs, but with automatic rewards. |
…r.cs Couldnt be me who forgot the summary...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Just out of curiosity, is there more anything that this pull request needs to be tweaked in order to get merged or has it been forgotten to be merged since may? I am just asking because last time I touched this pull request was in may and now it is almost at the end of june, so I am little curious. |
Since the websocket dev branch has been updated to latest changes from dev core in #33 , I do hope it is okay that I am submitted this pull request. Strike while the iron is hot, I suppose.
Let me know if there are anything that should be modified/changed, so it looks good with the rest of the structure that is already in place.